Device for facilitation of payments

ABSTRACT

A payment device comprising of a housing, a slot for insertion of a user instrument located on a front surface of the housing, and wherein the housing includes a smart card interface integrated circuit that is configured to read an EMV chip located on the user instrument, and a universal serial bus (USB) type C male connector configured to be inserted into a female connector on a computing device, wherein the USB type C male connector is located on a back surface of the housing, and wherein a size of the USB type C male connector is configured so that when the USB type C male connector is inserted into the female connector on the computing device, the back surface of the housing is within a distance of three centimeters of a surface of the computing device.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a Continuation of U.S. patent application Ser. No.16/565,194, filed Sep. 9, 2019, which is incorporated by reference inits entirety.

TECHNICAL FIELD

The present disclosure relates to payments, and more particularly to adevice that facilitates payments.

BACKGROUND

The payments landscape has changed drastically over the past decade.This is primarily due to financial technology platforms that haveallowed consumers to have simple and frictionless shopping experiencesonline, while also allowing consumers to transfer money to their familyand friends via their computers and mobile devices. Furthermore, withthe number of merchants and service providers that utilize financialtechnology platforms to accept payments from their customers, there is aneed for a compact payment device that can be coupled with a computingor mobile device to facilitate financial transactions.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a payment system, in accordance with an embodiment.

FIG. 2 illustrates the components of the payment device of FIG. 1 , inaccordance with an embodiment.

FIG. 3 illustrates a first view of the payment device of FIG. 1 , inaccordance with an embodiment.

FIG. 4 illustrates a second view of the payment device of FIG. 1 , inaccordance with an embodiment.

FIGS. 5 and 6 illustrates a third view and a fourth view of the paymentdevice of FIG. 1 , in accordance with an embodiment.

FIGS. 7 and 8 illustrates a fifth and sixth view of the payment deviceof FIG. 1 , in accordance with an embodiment.

FIG. 9 is a flowchart illustrating the operations of the client paymentapplication of FIG. 1 in facilitating the authentication of a user, inaccordance with an embodiment.

FIG. 10 is a flowchart illustrating the operations of the client paymentapplication of FIG. 1 in utilizing the payment device of FIG. 1 to loadbiometric information to a user instrument, in accordance with anembodiment.

FIG. 11 illustrates a view of a first alternative embodiment of thepayment device of FIG. 1 , in accordance with an embodiment.

FIG. 12 illustrates a view of a second alternative embodiment of thepayment device of FIG. 1 , in accordance with an embodiment.

FIG. 13 is a block diagram depicting the hardware components of thepayment system of FIG. 1 , in accordance with an embodiment.

DETAILED DESCRIPTION

Embodiments of the present disclosure provide a device and a method. Inthe example embodiment, the present disclosure describes a paymentdevice. The payment device comprises of a housing, a slot for insertionof a user instrument located on a front surface of the housing, andwherein the housing includes a smart card interface integrated circuitthat is configured to read an EMV chip located on the user instrument,and a universal serial bus (USB) type C male connector configured to beinserted into a female connector on a computing device, wherein the USBtype C male connector is located on a back surface of the housing, andwherein a size of the USB type C male connector is configured so thatwhen the USB type C male connector is inserted into the female connectoron the computing device, the back surface of the housing is within adistance of three centimeters of a surface of the computing device.

In an alternative embodiment, the payment device comprises a housing, aslot for insertion of a user instrument located on a front surface ofthe housing, and wherein the housing includes a smart card interfaceintegrated circuit that is configured to read an EMV chip located on theuser instrument, and a universal serial bus type C or micro-USB maleconnector configured to be inserted into a female connector on acomputing device, wherein the USB type C or micro-USB male connector islocated on a back surface of the housing, and wherein a size of the USBtype C or micro-USB male connector is configured so that when the USBtype C or micro-USB male connector is inserted into the female connectoron the computing device, the back surface of the housing is within adistance of two centimeters of a surface of the computing device.

In a further embodiment, the present disclosure describes a method asfollows. In response to detecting a user instrument inserted into apayment device, a computing device causes a request for biometricinformation to be provided to a user associated with the userinstrument. In response to detecting reception of the biometricinformation, the computing device causes the biometric information to beloaded onto the user instrument. The computing device updates a recordin a database associated with the user associated with the userinstrument to include the biometric information.

In the example embodiment, the present disclosure provides an improvedpayment device that is capable of reading a payment instrument, such asa credit card, by way of the payment instrument being inserted, andfurther is capable of communicating received payment information to amobile or computing device via USB-C or micro USB port in order tofacilitate a transaction. Furthermore, in one or more embodiments, thepayment device may be utilized by a payment application located on acoupled computing device or mobile device to receive authenticationinformation from a user for the purpose of authenticating a user. Forexample, in one or more embodiments, the payment device may be utilizedto receive an authentication instrument, such as an ID, or biometricinformation via a biometric receiver located on the payment device. Inaddition, in further embodiments, the payment device may be utilized toload biometric information onto an instrument, such as a financialinstrument.

Embodiments of the present disclosure will now be described in detailwith reference to the accompanying Figures.

FIG. 1 illustrates payment system 100, in accordance with an embodiment.In the example embodiment, payment system 100 includes payment device110, computing device 120 and payment server 140 interconnected vianetwork 130.

In the example embodiment, network 130 is the Internet, representing aworldwide collection of networks and gateways to support communicationsbetween devices connected to the Internet. Network 130 may include, forexample, wired, wireless or fiber optic connections. In otherembodiments, network 130 may be implemented as an intranet, a Bluetoothnetwork, a local area network (LAN), or a wide area network (WAN). Ingeneral, network 130 can be any combination of connections and protocolsthat will support communications between computing devices, such asbetween computing device 120 and payment server 140.

In the example embodiment, computing device 120 includes client paymentapplication 122. In the example embodiment, computing device 120 is amobile device, however, in other embodiments, computing device 120 maybe a desktop computer, a laptop computer, a tablet computer, a handhelddevice, a thin client, or any other electronic device or computingsystem capable of receiving and sending data to and from other computingdevices, such as payment server 140, via network 130. Computing device120 is described in more detail with regard to the figures.

In the example embodiment, client payment application 122 is aclient-side application, corresponding to the server-side paymentapplication 142, that is capable of transmitting requests to paymentapplication 142 and is further capable of providing received informationto a user of computing device 120 via a user interface. Client paymentapplication 122 is described in more detail with regard to the figures.

In the example embodiment, payment device 110 is a compact paymentdevice that includes a slot that is capable accepting an instrument,such as a financial instrument. In the example embodiment, paymentdevice 110 is further capable of reading an EMV chip financialinstrument, such as an EMV credit card. Furthermore, in the exampleembodiment, payment device 110 is capable of being coupled to computingdevice 120 via a USB-C or micro USB connection. Payment device 110 isdescribed in further detail with regard to the figures.

In the example embodiment, payment server 140 includes paymentapplication 142, database 144. In the example embodiment, payment server140 may be a desktop computer, a laptop computer, a tablet computer, amobile device, a handheld device, a thin client, or any other electronicdevice or computing system capable of receiving and sending data to andfrom other computing devices, such as computing device 120, via network130. Although not shown, optionally, payment server 140 can comprise acluster of servers executing the same software to collectively processrequests as distributed by a front-end server and a load balancer. Inthe example embodiment, payment server 140 is a computing device that isoptimized for the support of applications that reside on payment server140, such as payment application 142, and for the support of networkrequests related to payment application 142. Payment server 140 isdescribed in more detail with regard to the figures.

In the example embodiment, database 144 is a database that includesinformation that corresponds to one or more users (and/or merchants)associated with the service provider associated with payment server 140,such as one or more user preferences, user transactional history, usertransaction habits, user financial information, user authenticationinformation, user preferences, user connections (other users that a usermay be linked to, connected with, etc.), and additional userinformation. Furthermore, database 144 may include merchant informationsuch as merchant financial information, merchant transactional history,merchant authentication information, merchant preferences, andadditional merchant information. Database 144 is described in moredetail with regard to the figures.

In the example embodiment, payment application 142 is a server-sideapplication, corresponding to the client-side applications such asclient payment application 122. While in the example embodiment, paymentapplication 142 is a payment application, in other embodiments, paymentapplication 142 (and the corresponding client applications) may be asocial media application, an e-commerce application, or a different typeof application (that has payment ability). In the example embodiment,payment application 142 is capable of receiving information from clientapplications and further capable of responding to requests fromcorresponding client applications. In addition, in the exampleembodiment, payment application 142 is capable of detecting a purchasemade by a user via payment device 110 and computing device 120, andfurther capable of performing authentication and verification servicefor the transaction. Payment application 142 is described in more detailwith regard to the figures.

FIG. 2 illustrates the components of payment device 110, in accordancewith an embodiment. In the example embodiment, payment device 110includes universal serial bus (USB) interface 202 which may be coupledto USB power delivery (PD) 204. In the example embodiment, USB interface202 may connect to a male USB-C or micro USB connector. In otherembodiments, USB interface 202 may connect to a different type of USBmale connector. Furthermore, in the example embodiment, USB PD 204 mayallow for an external device to be charged via a USB-C/micro USBconnection by payment device 110 and may also allow for payment device110 to be charged by an external device. In the example embodiment,payment device 110 may also include smart card interface integratedcircuit (IC) 210. In the example embodiment, upon insertion of an EMVinstrument, such as a credit card containing an EMV chip, smart cardinterface IC 210 may read the EMV chip and forward the paymentinstrument information to microcontroller 206. Furthermore, as shown inFIG. 2 , microcontroller 206 may communicate information, such as thereceived payment information, to other devices, such as computing device120 via USB interface 202. In addition, in the example embodiment,payment device 110 may include WIFI/Bluetooth Low Energy Module 212which may allow payment device 110 to communicate with other devices viaWIFI or via a Bluetooth connection. Furthermore, as depicted, paymentdevice 110 may include biometric sensor 214 which may allow paymentdevice 110 to receive biometric information, such as fingerprintinformation. Received biometric information and information received viaWIFI/Bluetooth Low Energy Module 212 may be communicated to one or moreother devices via microcontroller 206. In the example embodiment,payment device 110 may also include memory 208.

FIG. 3 illustrates a first view of the payment device of FIG. 1 , inaccordance with an embodiment. In the example embodiment, FIG. 3 depictsa first view of payment device that includes male connector 310 that islocated on top of (and adjacent to) a back surface of (a housing of)payment device 110. In the example embodiment, male connector 310 is aUSB-C or micro-USB male connector that is capable of fitting into afemale USB-C or micro-USB connector located on another device, such ascomputing device 120. Furthermore, in the example embodiment, the firstview depicts a side surface 308 of payment device 110, a top surface 302of payment device 110, and a front surface 304 of payment device 110. Inthe example embodiment, the top surface 302 may be slope downwards inthe direction of front surface 304 so that the distance between topsurface 302 and the bottom surface of payment device 110 is smaller whennear front surface 304, as when compared to the distance between topsurface 302 and the bottom surface of payment device 110 when near theback surface of payment device 110. In other embodiments, top surface302 may not slope downward, and may instead run parallel to the bottomsurface of payment device 110, or in further embodiments, may slopeupwards in the direction of front surface 304.

In addition, in the example embodiment, the first view of payment device110 depicts a slot 306 that is located adjacent to front surface 304. Inthe example embodiment, slot 306 is surrounded by portions of frontsurface 304 (front surface 304 is located to the left, right, above andbelow slot 306). In other embodiments, slot 306 may be located adjacentto two walls or portions of front surface 304, or in other embodiments,adjacent to a single wall or portion of front surface 304.

FIG. 4 illustrates a second view of payment device 110, in accordancewith an embodiment. In the example embodiment, the second view ofpayment device 110 depicts a bottom surface 402 of payment device 110 aswell as male connector 310, slot 306, and front surface 304. In theexample embodiment, bottom surface 402 may be a flat surface, however,in other embodiments, bottom surface 402 may sloped upwards or downwardstowards front surface 304.

FIGS. 5 and 6 illustrates a third view and a fourth view of paymentdevice 110, in accordance with an embodiment. In the example embodiment,the third view and the fourth view depict a side view of the inside ofpayment device 110. In the example embodiment, the third view and thefourth view depict smart card interface IC 210 which is located insideof payment device 110 on top of a portion of slot 306. In the exampleembodiment, the depth of slot 306 as depicted in FIGS. 5 and 6 isconfigured to be the depth necessary so that an EMV chip located on apayment instrument that is inserted into slot 306 is in position to makecontact with smart card interface 210. In the example embodiment,position 502 may be the location of at least a portion of an EMV chip ofa payment instrument inserted in slot 306.

FIGS. 7 and 8 illustrates a fifth and sixth view of the payment deviceof FIG. 1 , in accordance with an embodiment. In the example embodiment,the fifth view is a front view of payment device 110. In the exampleembodiment, the fifth view depicts slot 306 surrounded by portions offront surface 304. Furthermore, in the example embodiment, the length702 and the height 704 of slot 306 are depicted. In the exampleembodiment, the height 704 of slot 306 may be less than 1 mm, to allowfor a credit card to fit tightly within the opening provided by slot306, but still minimize friction caused by inserting and pulling out acard. In further embodiments, the height 704 of slot 306 may be 1 mm orgreater. Furthermore, the length 702 may be less than 54 mm to allow fora credit card or similar instrument to fit tightly within the openingprovided by slot 306. In other embodiments, the length 702 may be 54 mmor greater.

In one specific example, the height 704 of slot 306 may be 0.88 mm (orwithin a threshold percentage of that value, such as within 10% of 0.88mm) and the length 702 may be 54.28 mm (or within a threshold percentageof that value, such as within 1% of 54.28 mm). In this example, asstated above, the height and length of slot 306 provides an opening thatallows a card to be inserted and removed while creating minimumfriction. If friction is minimized, the chances of payment device 110being pulled out computing device 120 when a card is removed is alsominimized. This may be especially important if payment device 110 isconnected to computing device 120 via a USB-C connection, because insome cases, a USB-C connection may provide less resistance when beingpulled than other types of connections, such as a micro-USB connection.

In the example embodiment, the sixth view is a back view of paymentdevice 110. In the example embodiment, the sixth view depicts backsurface 802 and male connector 310. In the example embodiment, maleconnector 310 is located on and adjacent to back surface 802, asdepicted. Furthermore, as stated above, male connector 310 is configuredto allow for connection to other computing devices, such as computingdevice 120, via a corresponding female connector (such as a female USB-Cor micro-USB connector). In addition, in the example embodiment, thesize of male connector 310 is configured in such a way that, when maleconnector 310 is inserted into a corresponding female connector ofanother computing device, such as computing device 120, a portion ofback surface 802 may make contact with a portion of a surface of theother computing device. In other embodiments, rather than making contactwith a portion of a surface of the other computing device, the size ofmale connector 310 is configured in a way such that, when male connector310 is inserted into a corresponding female connector of anothercomputing device, a portion of back surface 802 is within a 1 cmdistance of a portion from a surface of the other computing device. Inother embodiments, the size of male connector 310 may be so that, whenmale connector 310 is inserted into a corresponding female connector ofanother computing device, a portion of back surface 802 is within a 2 cmdistance, a 3 cm distance, or a greater distance from portion of asurface of the other computing device.

FIG. 9 is a flowchart illustrating the operations of client paymentapplication 122 in facilitating the authentication of a user, inaccordance with an embodiment. In the example embodiment, client paymentapplication 122 may detect a payment instrument has been inserted intopayment device 110 via communication with payment device 110 (step 902).In the example embodiment, upon the insertion of a payment instrumentinto payment device 110, smart card interface IC 210 may read paymentinformation from an EMV chip located on the payment instrument. Smartcard interface IC 210 may then communicate the payment information tomicrocontroller 206 which in turn may transmit the payment informationto client payment application 122 via USB interface 202. In the exampleembodiment, with regard to the operations in FIG. 9 , payment device 110is connected to computing device 120 via a USB-C or micro-USBconnection.

In one or more embodiments, if payment device 110 detects an error inreading the inserted payment instrument, payment device 110 (viamicrocontroller 206) may transmit a signal to computing device 120 tocause an application, such as client payment application 122, that iscapable of taking pictures to launch so a picture of the paymentinstrument may be taken.

In the example embodiment, upon detection of the payment instrument,client payment application 122 may prompt the user associated with thepayment instrument for authentication information (step 904). In theexample embodiment, client payment application 122 may provide aninterface on computing device 120 to prompt the user associated with thepayment instrument for authentication information. In one or moreembodiments, client payment application 122 may utilize a fingerprintreader on computing device 120 to receive fingerprint information, or infurther embodiments, may prompt the user associated with the paymentinstrument to provide user identification information via the interfaceprovided on computing device 120. In other embodiments, client paymentapplication 122 may utilize a fingerprint reader located on paymentdevice 110 to obtain fingerprint information from the user associatedwith the payment instrument.

In additional embodiments, upon the detection by microcontroller 206that a payment instrument has been inserted into payment device 110,microcontroller 206 may transmit a signal to computing device 120 thatmay cause client payment application 122 to launch and provide theinterface described above.

In the example embodiment, client payment application 122 may transmitreceived authentication information to payment application 142 to causea verification process of the received authentication information (step906). In the example embodiment, if payment application 142 determinesthat the authentication information has been verified, paymentapplication 142 may cause a payment associated with the verificationrequest to be processed. If the payment is processed, a notification maybe transmitted to client payment application 122, which may in turndisplay the notification to the user associated with the paymentinstrument. If the authentication information is not verified, paymentapplication 142 may cause the payment to be denied and may furthertransmit a notification that the payment was denied to client paymentapplication 122.

In the example embodiment, payment application 142 may refer to database144 to identify if received authentication information corresponds toauthentication information stored in association to the user associatedwith the payment instrument.

FIG. 10 is a flowchart illustrating the operations of client paymentapplication 122 in utilizing payment device 110 to load biometricinformation to a user instrument, in accordance with an embodiment. Inthe example embodiment, client payment application 122 may detect a userinstrument has been inserted into payment device 110 via communicationwith payment device 110 (step 1002). In the example embodiment, asstated above, upon the insertion of a user instrument into paymentdevice 110, smart card interface IC 210 may read information from an EMVchip located on the user instrument. Smart card interface IC 210 maythen communicate the user instrument information to microcontroller 206which in turn may transmit the user instrument information to clientpayment application 122 via USB interface 202. In the exampleembodiment, with regard to the operations in FIG. 10 , payment device110 is connected to computing device 120 via a USB-C or micro-USBconnection. In the example embodiment, a user instrument may include apayment instrument, a user identification card, another type offinancial instrument, or another user instrument.

In the example embodiment, upon detection of the user instrument, clientpayment application 122 may prompt the user associated with the userinstrument for biometric information (step 1004). In the exampleembodiment, client payment application 122 may provide an interface oncomputing device 120 to prompt the user associated with the userinstrument for authentication information. In one or more embodiments,client payment application 122 may utilize a biometric component, suchas a fingerprint reader on computing device 120, to receive biometricinformation, or in further embodiments, may prompt the user associatedwith the user instrument to provide biometric information via theinterface provided on computing device 120. In other embodiments, clientpayment application 122 may utilize a biometric component, such as afingerprint reader located on payment device 110, to obtain biometricinformation from the user associated with the user instrument.

In the example embodiment, client payment application 122 may detectreception of biometric information from the user associated with theuser instrument (step 1006), and based on reception of the biometricinformation, may transmit the biometric information to microcontroller206 and cause the biometric information to be loaded onto the EMV chipof the user instrument (step 1008). In addition, a user database, suchas database 144 may be updated, by client payment application 122 orpayment application 142 to associate the biometric information with theuser.

In additional embodiments, upon the detection by microcontroller 206that a user instrument has been inserted into payment device 110,microcontroller 206 may transmit a signal to computing device 120 thatmay cause client payment application 122 to launch and provide theinterface described above.

In other embodiments, payment device 110, such as microcontroller 206may detect the insertion of the payment instrument as described above(such as via smart card interface IC 210) and may further prompt theuser for biometric information via an indication signal or via a displaylocated on payment device 110. In one or more embodiments, theindication signal may include a visual signal, such as a lightindicator, an audio signal, or a haptic signal. Furthermore,microcontroller 206 may detect reception of the biometric informationfrom the user associated with the user instrument and may cause thebiometric information to be loaded onto an EMV chip located on the userinstrument.

In further embodiments, payment device 110 may include logic that maydetect if a payment instrument corresponding to one or more userprofiles has been inserted into slot 306. For example, a single paymentinstrument may correspond to multiple users, such as a father and son,with each user having different spending limits and restrictions. Eachprofile may correspond to a fingerprint or other biometric information,so that when the payment instrument is utilized, a point of saleterminal may require the input of the associated biometric informationin order for a determination to be made as to which user is utilizingthe payment instrument. Therefore, if the payment instrument is insertedinto a point of sale terminal and the father inputs his fingerprint, thespending limits associated with the father would be determined to beapplicable to the transaction. Furthermore, fraud determinations, andother payment related terminations may be at least partially based ontransactional activity associated with the user profile. Therefore, forthis type of payment instrument, payment device 110 may be utilized tocreate the profiles by allowing for fingerprint or biometric informationto be loaded onto the payment instrument during activation (in themanner described above).

In other embodiments, payment device 110 may be used in conjunction withcomputing device 120 to associate a profile on a payment instrument witha fingerprint or alter/change a fingerprint associated with an existingprofile. For example, client payment application 122 may be launched oncomputing device 120 (with computing device 120 connected via maleconnector 310 to payment device 110) and further the payment instrumentmay be inserted into payment device 110. In one or more embodiments,client payment application 122 may detect the insertion of the paymentinstrument and further provide the user with the option of creating aprofile or altering an existing profile. The user may then utilize afingerprint reader located on computing device 120 or on payment device110 to provide fingerprint information and associate the providedfingerprint information with a user profile. Client payment application122 may then transmit the profile information to payment device 110 andpayment device 110 may then load the profile information onto an EMVchip of the payment instrument. In other embodiments, the same steps maybe followed to load a profile onto a user instrument or an instrumentthat is not used for payments.

FIG. 11 illustrates a view of a first alternative embodiment of paymentdevice 110, in accordance with an embodiment. In the example embodiment,the first alternative embodiment of payment device 110 includescontactless component 1104 which may utilize a radio-frequencyidentification (RFID) reader/component or a near field communication(NFC) component to detect the presence of a contactless card (such as acontactless credit card) or a mobile phone/electronic device that isbeing utilized to provide a payment. In the example embodiment,contactless component 1104 may communicate with microcontroller 206 inorder to transmit payment information to another computing device, suchas computing device 120, as described above. In the example embodiment,the first alternative embodiment of payment device 110 includesfingerprint reader 1102. In the example embodiment, fingerprint reader1102 allows for the reception of fingerprint information from a userassociated with a payment instrument being utilized with payment device110. In the example embodiment, fingerprint reader 1102 may allow foradditional authentication information to be received by payment device110 for the purposes of verification or may be utilized as describedabove to load biometric or fingerprint information onto a userinstrument, such as a credit card to provide an additional layer ofsecurity. As depicted in FIG. 11 , fingerprint reader 1102 andcontactless component 1104 may be located on top surface 302, however,in other embodiments, may be located on a different surface of paymentdevice 110.

FIG. 12 illustrates a view of a second alternative embodiment of paymentdevice 110, in accordance with an embodiment. In the example embodiment,the second alternative embodiment includes fingerprint readers 1202 and1204. In the example embodiment, the second alternative embodiment mayinclude two additional fingerprint readers 1202 and 1204 that arelocated on bottom surface 402 in addition to the fingerprint reader 1102located on top surface 302. In other embodiments, fingerprint readers1202 and 1204 may be present on payment device 110 without additionalfingerprint readers being present on payment device 110. While FIG. 12depicts fingerprint readers 1202 and 1204 being located on bottomsurface 402, in other embodiments, fingerprint readers 1202 and 1204 maybe located on a different surface of payment device 110.

The foregoing description of various embodiments of the presentdisclosure has been presented for purposes of illustration anddescription. It is not intended to be exhaustive nor to limit thedisclosure to the precise form disclosed. Many modifications andvariations are possible. Such modifications and variations that may beapparent to a person skilled in the art of the disclosure are intendedto be included within the scope of the disclosure as defined by theaccompanying claims.

Furthermore, this specification includes references to “the exampleembodiment,” “other embodiments,” “one or more embodiments, “furtherembodiments”, “additional embodiments”, and the like. The appearances ofthese phrases do not necessarily refer to the same embodiment.Particular features, structures, or characteristics may be combined inany suitable manner consistent with this disclosure.

The scope of the present disclosure includes any feature or combinationof features disclosed herein (either explicitly or implicitly), or anygeneralization thereof, whether or not it mitigates any or all of theproblems addressed by various described embodiments. Accordingly, newclaims may be formulated during prosecution of this application (or anapplication claiming priority thereto) to any such combination offeatures.

FIG. 13 depicts a block diagram of components of one or more devices ofpayment system 100, such as computing device 120, in accordance with anembodiment. It should be appreciated that FIG. 13 provides only anillustration of one implementation and does not imply any limitationswith regard to the environments in which different embodiments may beimplemented. Many modifications to the depicted environment may be made.In the example embodiment, as depicted, payment device 110 may includethe components described in FIG. 2 , however in one or more embodiments,payment device 110 may include one or more of the components depicted inFIG. 13 as well.

Computing devices may include one or more processors 1302, one or morecomputer-readable RAMs 1304, one or more computer-readable ROMs 1306,one or more computer readable storage media 1308, device drivers 1312,read/write drive or interface 1314, network adapter or interface 1316,all interconnected over a communications fabric 1318. Communicationsfabric 1318 may be implemented with any architecture designed forpassing data and/or control information between processors (such asmicroprocessors, communications and network processors, etc.), systemmemory, peripheral devices, and any other hardware components within asystem.

One or more operating systems 1310, and one or more application programs1311, for example, payment application 142, are stored on one or more ofthe computer readable storage media 1308 for execution by one or more ofthe processors 1302 and by utilizing one or more of the respective RAMs1304 (which typically include cache memory). In the illustratedembodiment, each of the computer readable storage media 1308 may be amagnetic disk storage device of an internal hard drive, CD-ROM, DVD,memory stick, magnetic tape, magnetic disk, optical disk, asemiconductor storage device such as RAM, ROM, EPROM, flash memory orany other computer-readable tangible storage device that can store acomputer program and digital information.

Computing devices may also include a R/W drive or interface 1314 to readfrom and write to one or more portable computer readable storage media1326. Application programs 1311 on the computing devices may be storedon one or more of the portable computer readable storage media 1326,read via the respective R/W drive or interface 1314 and loaded into therespective computer readable storage media 1308.

Computing devices may also include a network adapter or interface 1316,such as a TCP/IP adapter card or wireless communication adapter (such asa 4G wireless communication adapter using OFDMA technology). Applicationprograms 1311 on the computing devices may be downloaded to thecomputing devices from an external computer or external storage devicevia a network (for example, the Internet, a local area network or otherwide area network or wireless network) and network adapter or interface1316. From the network adapter or interface 1316, the programs may beloaded onto computer readable storage media 1308. The network maycomprise copper wires, optical fibers, wireless transmission, routers,firewalls, switches, gateway computers and/or edge servers.

Computing devices may also include a display screen 1320, and externaldevices 1322, which may include, for example a keyboard, a computermouse and/or touchpad. Device drivers 1312 interface to display screen1320 for imaging, to external devices 1322, and/or to display screen1320 for pressure sensing of alphanumeric character entry and userselections. The device drivers 1312, R/W drive or interface 1314 andnetwork adapter or interface 1316 may comprise hardware and software(stored on computer readable storage media 1308 and/or ROM 1306).

The programs described herein are identified based upon the applicationfor which they are implemented in a specific embodiment. However, itshould be appreciated that any particular program nomenclature herein isused merely for convenience, and thus the disclosure should not belimited to use solely in any specific application identified and/orimplied by such nomenclature.

Based on the foregoing, a computer system, method, and computer programproduct have been disclosed. However, numerous modifications andsubstitutions can be made without deviating from the scope of thepresent disclosure. Therefore, the various embodiments have beendisclosed by way of example and not limitation.

Various embodiments of the present disclosure may be a system, a method,and/or a computer program product. The computer program product mayinclude a computer readable storage medium (or media) having computerreadable program instructions thereon for causing a processor to carryout aspects of the present disclosure.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present disclosure may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, configuration data for integrated circuitry, oreither source code or object code written in any combination of one ormore programming languages, including an object oriented programminglanguage such as Smalltalk, C++, or the like, and procedural programminglanguages, such as the “C” programming language or similar programminglanguages. The computer readable program instructions may executeentirely on the user's computer, partly on the user's computer, as astand-alone software package, partly on the user's computer and partlyon a remote computer or entirely on the remote computer or server. Inthe latter scenario, the remote computer may be connected to the user'scomputer through any type of network, including a local area network(LAN) or a wide area network (WAN), or the connection may be made to anexternal computer (for example, through the Internet using an InternetService Provider). In some embodiments, electronic circuitry including,for example, programmable logic circuitry, field-programmable gatearrays (FPGA), or programmable logic arrays (PLA) may execute thecomputer readable program instructions by utilizing state information ofthe computer readable program instructions to personalize the electroniccircuitry, in order to perform aspects of the present disclosure.

Aspects of the present disclosure are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of thedisclosure. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present disclosure. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the blocks may occur out of theorder noted in the Figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

What is claimed is:
 1. A payment device, comprising: a housing; a slotfor insertion of a user instrument located on a front surface of thehousing, and wherein the housing includes a smart card interfaceintegrated circuit (IC) that is configured to read an EMV chip locatedon the user instrument; and a universal serial bus (USB) type C or amicro-USB male connector configured to be inserted into a femaleconnector on a computing device, wherein the USB type C or micro-USBmale connector is located on a back surface of the housing, and whereinthe payment device is configured to (i) upon detecting that the userinstrument has been inserted into the slot, transmit a signal to thecomputing device, wherein the signal causes the computing device tolaunch a first interface of a payment application located on thecomputing device, (ii) obtain biometric data of a user from the paymentapplication of the computing device, and (iii) load the biometric datato the EMV chip of the user instrument.
 2. The payment device of claim1, wherein, when the payment device is connected to the computingdevice, the back surface of the housing is within a distance of threecentimeters of a surface of the computing device.
 3. The payment deviceof claim 1, further comprising one or more fingerprint readers locatedon a surface of the payment device.
 4. The payment device of claim 1,further comprising two or more fingerprint readers located on a surfaceof the payment device.
 5. The payment device of claim 1, furthercomprising a contactless component that is configured to receiveinformation from the user instrument.
 6. The payment device of claim 1,wherein, upon receiving fingerprint information via a fingerprint readerlocated on a surface of the payment device, the payment device isfurther configured to transmit a second signal to the computing devicethat causes the computing device to initiate a verification process ofthe received fingerprint information.
 7. The payment device of claim 1,wherein the smart card interface IC is further configured to, inresponse to reading payment information from the EMV chip located on theuser instrument, transmit the payment information to the computingdevice via a microcontroller of the payment device.
 8. A system,comprising: a non-transitory memory; one or more processors coupled withthe non-transitory memory and configured to read instructions from thenon-transitory memory to cause the system to perform operationscomprising: detecting an insertion of a user instrument into a slotlocated on a front surface of a housing of a payment device; and inresponse to the detecting, (i) transmitting a signal to a computingdevice, wherein the signal causes the computing device to launch a firstinterface of a payment application located on the computing device, (ii)obtaining biometric data of a user from the computing device, and (iii)loading the biometric data to an EMV chip of the user instrument,wherein: the housing includes a smart card interface integrated circuit(IC) that is configured to read the EMV chip located on the userinstrument; and the payment device includes a universal serial bus (USB)type C or a micro-USB male connector that is located on a back surfaceof the housing and configured to be inserted into a female connector onthe computing device.
 9. The system of claim 8, wherein, when thepayment device is connected to the computing device, the back surface ofthe housing is within a distance of three centimeters of a surface ofthe computing device.
 10. The system of claim 8, wherein the paymentdevice further includes one or more fingerprint readers located on asurface of the payment device.
 11. The system of claim 8, wherein thepayment device further includes two or more fingerprint readers locatedon a surface of the payment device.
 12. The system of claim 8, whereinthe payment device further includes a contactless component that isconfigured to receive information from the user instrument.
 13. Thesystem of claim 8, wherein the operations further comprise in responseto receiving fingerprint information via a fingerprint reader located ona surface of the payment device, transmitting a second signal to thecomputing device that causes the computing device to initiate averification process of the received fingerprint information.
 14. Thesystem of claim 8, wherein the smart card interface IC is furtherconfigured to, in response to reading payment information from the EMVchip located on the user instrument, transmit the payment information tothe computing device via a microcontroller of the payment device.
 15. Amethod, comprising: detecting, by one or more hardware processorsassociated with a payment device, an insertion of a user instrument intoa slot located on a front surface of a housing of the payment device;and in response to the detecting, (i) transmitting a signal to acomputing device, wherein the signal causes the computing device tolaunch a first interface of a payment application located on thecomputing device, (ii) obtaining biometric data of a user from thecomputing device, and (iii) loading the biometric data to an EMV chip ofthe user instrument, wherein: the housing includes a smart cardinterface integrated circuit (IC) that is configured to read an EMV chiplocated on the user instrument; and the payment device includes auniversal serial bus (USB) type C or a micro-USB male connector that islocated on a back surface of the housing and configured to be insertedinto a female connector on the computing device.
 16. The method of claim15, wherein, when the payment device is physically connected to thecomputing device, the back surface of the housing is within a distanceof three centimeters of a surface of the computing device.
 17. Themethod of claim 15, wherein the payment device further includes one ormore fingerprint readers located on a surface of the payment device. 18.The method of claim 15, wherein the payment device further includes acontactless component that is configured to receive information from theuser instrument.
 19. The method of claim 15, further comprising inresponse to receiving fingerprint information via a fingerprint readerlocated on a surface of the payment device, transmitting a second signalto the computing device that causes the computing device to initiate averification process of the received fingerprint information.
 20. Themethod of claim 15, wherein the smart card interface IC is furtherconfigured to, in response to reading payment information from the EMVchip located on the user instrument, transmit the payment information tothe computing device via a microcontroller of the payment device.